Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove legacy v2 support. #272

Closed
wants to merge 1 commit into from
Closed

Remove legacy v2 support. #272

wants to merge 1 commit into from

Conversation

isoos
Copy link
Owner

@isoos isoos commented Dec 14, 2023

No description provided.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0bdc0d6) 85.56% compared to head (6b73972) 85.56%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #272   +/-   ##
=======================================
  Coverage   85.56%   85.56%           
=======================================
  Files          25       25           
  Lines        2244     2244           
=======================================
  Hits         1920     1920           
  Misses        324      324           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@isoos
Copy link
Owner Author

isoos commented Dec 14, 2023

Anything against this? We have released v3 about a month ago, with a patch releases every week, so I think we have at least a moderate amount of exposure from users.

/cc @simolus3 @osaxma

@simolus3
Copy link
Contributor

I have migrated all my code to v3 so I have nothing against this, but

so I think we have at least a moderate amount of exposure from users

may be a bit optimistic after one month? Looking at the top packages depending on postgres, drift and postgres_crdt are the only two packages on the first page supporting postgres v3. package:postgres_pool should potentially be marked as discontinued with postgres as a replacement, but maybe we should ask authors of the other packages if they have issues with the v3 API preventing them to upgrade?

On the other hand, folks depending on the compatibility layer can always upgrade to 3.0.x first, do the migration and then upgrade all the way to the latest 3.1+ version. But perhaps this should be mentioned in the previous changelog entry (suggest upgrading to postgres: >=3.0.0 <3.1.0 first)?

@isoos
Copy link
Owner Author

isoos commented Dec 15, 2023

Good points.

I've now discontinued postgres_pool and cockroachdb_pool (which has been neglected for a while, but I didn't have the need to update my app that used it). Which reminded me that I wanted to implement an event notification thing for the pool support, and potentially for regular connections too. I have an app that produced really useful metrics and logs based on these events, but it is no longer active/running.

Upgrading for frameworks is a tough call, and maybe I'm too optimistic about it. It is probably not much overhead at this point to keep it.

@isoos isoos closed this Dec 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants